Related issues

• INTP-368

Proposed changes

This pull request introduces a set of maintenance and reliability improvements targeting both the continuous integration workflow as well as the test infrastructure and client error reporting. The following major changes are included:

1. CI Workflow Repository Reference Fix:

   • The repository reference in the GitHub Actions workflow (ci.yml) is updated from ankipalace/ankihub to AnkiHubSoftware/ankihub to reflect the correct repository location.
   • The checkout step name is also adjusted for clarity.

2. Improved Client Error Reporting:

   • The string representation of the AnkiHubHTTPError exception in ankihub_client.py now includes the response content, not just the status code and reason. This change provides more diagnostic context in error logs, especially for unexpected HTTP failures.

   try:
       response_text = self.response.text
   except Exception:
       response_text = "Unable to read response content"
   return f"AnkiHub request error: {self.response.status_code} {self.response.reason}\n{response_text}"

3. Type Consistency Fix in Tutorial Code:

   • TutorialStep.back_callback's type is corrected for consistency with next_callback: it now expects a Callable accepting a callback argument, not just a parameterless lambda.

4. Robust Database Restore in Integration Tests:

   • The integration test fixture in test_client.py has improved logic for database restoration:
     • Instead of using a standard pg_restore --clean, a filtered table of contents (TOC) is generated that skips the SCHEMA entry. This avoids attempts to drop the schema, which can fail if extensions are present.
     • The TOC filtering is performed via pg_restore -l | grep -v ' SCHEMA ' and the filtered TOC (restore_toc.list) is then used with the -L option of pg_restore.
     • This ensures a more reliable and repeatable restore of test databases, especially when using Postgres extensions (e.g., pg_trgm, vector).
     • Additional options --if-exists and --jobs=4 help with idempotency and faster restore operations.

Further comments

PR Dependency: To make the tests for this PR pass, the changes in this PR (https://github.com/AnkiHubSoftware/ankihub/pull/3340) need to be merged into the ankihub repository first. The integration tests rely on backend changes introduced there.

Test DB Restore Logic: The main motivation for the update was to address unreliable restores when using Postgres extensions, which can cause DROP SCHEMA to fail and require container-level intervention. We now surgically reset only the necessary DB objects for tests while maintaining extensions.

Richer HTTP Error Messages: These should make debugging network/client integration issues faster—the raw response often includes error messages from the API that were previously hidden from the logs.

Potential risks: - The new TOC filtering method for pg_restore assumes consistent Postgres dump behavior; future major Postgres version upgrades may alter this syntax or require TOC filtering tweaks.

In rare edge cases, errors in reading the HTTP response content could still obscure the payload (handled defensively).